Solution: MenloSecurity
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Publisher | Menlo Security |
| Support Tier | Partner |
| Support Link | https://www.menlosecurity.com/customers/support |
| Categories | Security - Threat Protection |
| Version | 3.0.0 |
| Author | Menlo Security - support@menlosecurity.com |
| First Published | 2026-02-26 |
| Last Updated | 2026-10-28 |
| Solution Folder | MenloSecurity |
| Marketplace | Azure Marketplace · Popularity: ⚪ Very Low (0%) |
The Menlo Security solution for Microsoft Sentinel ingests Audit, Bandwidth, and Web proxy logs from the Menlo Security cloud platform into custom Log Analytics tables (MenloAudit_CL, MenloBandwidth_CL, MenloWeb_CL) for threat detection, investigation, and response. Logs are collected by three timer-triggered Azure Functions that poll the Menlo Security Log Fetch API and ship events via the Azure Monitor Logs Ingestion API using a Data Collection Endpoint (DCE) and Data Collection Rule (DCR).
Underlying Microsoft Technologies used:
This solution takes a dependency on the following technologies, and some of these dependencies either may be in Preview state or might result in additional ingestion or operational costs:
a. Azure Monitor Logs Ingestion API (DCE/DCR)
This solution provides 1 data connector(s):
This solution uses 3 table(s):
| Table | Used By Connectors | Used By Content |
|---|---|---|
MenloAudit_CL |
Menlo Security | - |
MenloBandwidth_CL |
Menlo Security | - |
MenloWeb_CL |
Menlo Security | - |
📄 Source: MenloSecurity/README.md
The Menlo Security solution ingests security logs from the Menlo Security cloud platform into Microsoft Sentinel. Menlo Security protects organizations from browser-based threats using an isolation-first approach; this solution brings that telemetry into Microsoft Sentinel for threat detection, investigation, and response.
Note: This solution is currently in public preview.
The solution installs a single data connector that runs as three independent, timer-triggered Azure Functions — one per log type. Each function polls the Menlo Security Log Fetch API every 3 minutes and ships events to a custom Log Analytics table via the Azure Monitor Logs Ingestion API. No inbound network access to your environment is required.
| Log type | Log Analytics table | Description |
|---|---|---|
| Audit | MenloAudit_CL |
Admin and policy change events |
| Bandwidth | MenloBandwidth_CL |
Proxy bandwidth usage per user and domain |
| Web | MenloWeb_CL |
Web request events including URLs, categories, and threat verdicts |
All connector resources are deployed into a dedicated resource group named MenloSecurityLogs, created in the same Azure region as your Log Analytics workspace. The custom tables are created in your existing workspace's resource group.
| Resource | Purpose |
|---|---|
| Azure Function App (Flex Consumption, Linux, Python) | Hosts the three timer-triggered ingestion functions |
| Azure Storage Account | Function host state, deployment package, and per-log-type last-sync timestamps |
| Azure Key Vault | Stores the Menlo API token as a secret (resolved via Key Vault reference) |
| Application Insights | Function execution, error, and performance monitoring (workspace-based) |
| Data Collection Endpoint (DCE) | HTTPS ingestion endpoint that receives logs from the Function App |
| Data Collection Rule (DCR) | Applies KQL type transforms and routes logs to the correct tables |
| Log Analytics tables (3) | MenloAudit_CL, MenloBandwidth_CL, MenloWeb_CL |
The Function App authenticates to Azure using a System-Assigned Managed Identity — no passwords, connection strings, or client secrets are used for any Azure resource access. Inbound HTTP traffic to the Function App is denied; timer triggers require no inbound access.
/api/rep/v2/fetch/client_select endpoint, obtained from the Menlo Security admin console).[Content truncated...]
| Version | Date Modified (DD-MM-YYYY) | Change History |
|---|---|---|
| 3.0.0 | 13-10-2026 | Initial solution release. Adds the Menlo Security data connector, which ingests Audit, Bandwidth, and Web proxy logs into the MenloAudit_CL, MenloBandwidth_CL, and MenloWeb_CL custom Log Analytics tables via three timer-triggered Azure Functions and the Azure Monitor Logs Ingestion API (DCE/DCR). |
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊